Programmable adapters for detachably connecting robotic peripherals to adaptively retool robots

ABSTRACT

Apparatus and methods for adaptively retooling robots include programmable adapters for detachably connecting at least one robotic peripheral to a robot, providing peripheral information associated with the robotic peripheral, and causing the robot to adaptively reconfigure based on the peripheral information.

FIELD

The present disclosure relates generally to programmable adapters fordetachably connecting at least one robotic peripheral to a robot,providing peripheral information associated with the robotic peripheral,and causing the robot to adaptively reconfigure based on the peripheralinformation.

BACKGROUND

Industrial robotic automation has seen significant adoption inlarge-scale manufacturing for tasks such as welding, cutting, stamping,painting, heavy material handling, precision material machining, and thelike. Robotic automation in manufacturing offers many benefits, such ashigher productivity, lower production costs, better quality, greaterconsistency, and the like. However, robotic automation comes with ahefty price tag. Enterprises engaging in large-scale manufacturing canleverage scale of production to amortize high initial costs and overheadassociated with robotic automation. Therefore, for large-scalemanufacturing enterprises, benefits of robotic automation justify itshefty price tag.

Successful adoption of robotic automation in large-scale manufacturinghas led to a long-standing desire for small and medium-sizedmanufacturing enterprises (“SMEs”) to also significantly adopt roboticautomation. However, SMEs typically engage in manufacturing processes atsmaller scales, and thus SMEs are less able to leverage production scaleto amortize high initial costs and overhead associated with roboticautomation. Therefore, there is a need for apparatus and methods forovercoming these and other problems presented by the prior art.

SUMMARY

With robotic technology continuing to advance and becoming moreaccessible, SMEs are eager to join large-scale manufacturing enterprisesin adopting and reaping the benefits of robotic automation. However,compared to large-scale manufacturing enterprises, SMEs typicallyimplement production processes at smaller scales, and thus SMEs are lessable to leverage production scale to amortize high initial costs andoverhead associated with robotic automation. Moreover, productionprocesses implemented by SMEs typically involve shorter productioncycles, entail higher product variability, and/or demand quickerdesign-to-product turnaround. Consequently, SMEs need to attach, set up,and swap robotic peripherals more frequently than large-scalemanufacturing enterprises, which present SMEs with several challenges.For example, how can robotic peripherals be attached to and swapped outof a robot in a robotic system rapidly and in a repeatable manner? Howcan the robotic system efficiently obtain information associated withattached robotic peripherals? How can the robotic system adapt to theattached robotic peripherals so the robot can effectively and safely usethe attached robotic peripherals? Therefore, a need exists for roboticapparatus and methods that can be quickly and efficiently adapted toautomate different types of production tasks. There is also growinginterest in the ease-of-use of programmable robotic systems for noviceend-users.

Various embodiments of the present disclosure include examples of arobotic apparatus that detachably yet rigidly connects one or morerobotic peripherals to a robot in a repeatable manner, providesperipheral profile information associated with the robotic peripherals,and causes the robot to adaptively reconfigure based on the peripheralprofile information. The robotic apparatus can utilize easy-to-installand/or hot-swappable robotic peripherals, such as sensors, endeffectors, tooling, and other robotic peripherals. The robotic apparatusenables users of the robot to efficiently and intuitively retool therobot and adaptively automate the robot for different types of tasks,which decreases expenditure of resources such as time, effort, andexpertise required for robotic automation, and thus enhancing the valueand appeal of robotic automation for manufacturing enterprises of allsizes, particularly for SMEs that typically implement smaller-scaleproduction processes.

Embodiments of the present disclosure relate to apparatus and methodsfor detachably connecting robotic peripherals to a robot, providingperipheral information associated with the robotic peripherals, andcausing the robot to adaptively reconfigure based on the peripheralinformation. Specifically, an apparatus for adaptive robotic retoolingcomprises a peripheral adapter including a first side that has aperipheral flange, a second side for connecting the peripheral adapterto a robotic peripheral, a peripheral data storage unit for storing aperipheral profile of the robotic peripheral, and a peripheralcommunication device for communicating peripheral information in theperipheral profile, wherein the peripheral data storage unit and theperipheral communication device are communicatively linked; a roboticadapter including a first side that has a robotic flange, a second sidefor connecting the robotic adapter to a robot, and a roboticcommunication device for providing a communication link with theperipheral communication device; and a connector including a couplingmechanism for mechanically coupling the peripheral flange to the roboticflange, thereby forming a detachable connection between the peripheraladapter and the robotic adapter and causing the robotic adapter to querythe peripheral adapter for the peripheral information via thecommunication link.

Additional objects and advantages of the embodiments of the disclosurewill be set forth in part in the description which follows, and in partwill be obvious from the description, or may be learned by practice ofthe embodiments. The objects and advantages of the embodiments will berealized and attained by means of the elements and combinationsparticularly pointed out in the appended claims. It is to be understoodthat both the foregoing general description and the following detaileddescription are exemplary and explanatory only and are not restrictiveof the embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-C illustrate an embodiment of a robotic retooling apparatus foradaptively retooling a robot in a robotic system that detachablyconnects robotic peripherals to the robot and causes the robotic systemto adaptively reconfigure the robot based on the detachably connectedrobotic peripherals, consistent with the principles of the presentdisclosure.

FIGS. 2 and 3 are flow diagrams illustrating examples of methodsperformed by the robotic retooling apparatus to adaptively retool therobot, consistent with embodiments of the present disclosure.

FIGS. 4A and 4B illustrate an embodiment of a peripheral adapter and adocking unit of the robotic retooling apparatus, consistent with theprinciples of the present disclosure.

FIG. 5 is a flow diagram illustrating an example of a method performedby the docking unit to program peripheral adapters with peripheralprofiles of robotic peripherals designated for the peripheral adapters,consistent with embodiments of the present disclosure.

FIG. 6 is an example computer system for performing the disclosedembodiments, consistent with the present disclosure.

DETAILED DESCRIPTION

Reference will now be made in detail to example embodiments, which areillustrated in the accompanying drawings. When appropriate, the samereference numbers are used throughout the drawings to refer to the sameor like parts.

For simplicity and illustrative purposes, the principles of the presentdisclosure are described by referring mainly to various embodimentsthereof. However, one of ordinary skill in the art would readilyrecognize that the same principles are equally applicable to, and can beimplemented in, all types of information and systems, and that any suchvariations do not depart from the true spirit and scope of the presentdisclosure. Moreover, in the following detailed description, referencesare made to the accompanying figures, which illustrate specificembodiments. Electrical, mechanical, logical and structural changes maybe made to the various embodiments without departing from the spirit andscope of the present disclosure. The following detailed description is,therefore, not to be taken in a limiting sense and the scope of thepresent disclosure is defined by the appended claims and theirequivalents.

In the present disclosure, the word “robot” will be used instead ofrobotic manipulator or robotic apparatus. Typically, a robot is anindustrial robotic manipulator or a set of industrial roboticmanipulators for automated or semi-automated production applications. Anend effector can be a tool effector attached to a robot at a connectionsite of the robot or a tool grasped or held by a gripper-type endeffector attached to the robot. The following general definitions willhe used herein. Robotic hardware module: a physical device or toolingthat can be connected (e.g., attached, coupled, linked, etc.) to a robotand/or disconnected (e.g., detached, decoupled, delinked, and the like)from the robot. Peripheral or robotic peripheral: a robotic hardwaremodule that can be connected to a robot to provide some physicalinteraction, manipulation, and/or sensing capability. Active peripheral:a peripheral that can communicate with a robot via one or morecommunication channels such as a network connection, a Universal SerialBus (“USB”) connection, etc., and may or may not have a physicalconnection with the robot. Passive peripheral: a peripheral with only amechanical connection to a robot. Software module: a unit of softwarethat encapsulates some processing, algorithmic, or inference capabilityaccessible via at least one defined interface. Software component: aninstantiated software module. User interface (“UI”): a visual, gestural,haptic, or audio interface that allows for user interaction with arobot. UI component: a widget or graphical element that can accept inputand events from a user and provide information to the user. Roboticsystem: an integrated, interconnected collection of at least one robotand one or more hardware and/or software modules/components thatcommunicate with and control the robot, manage and store informationassociated with the robot, and/or interact with at least one user toconfigure and operate the robot. Detachable connection: a physicalconnection between a robotic hardware module and at least one otherrobotic hardware module discrete from the first module that can beformed and broken in a repeatable manner.

Large-scale manufacturing enterprises typically implement large-scaleproduction processes and leverage production scale to amortize costsassociated with robotic automation. Consequently, large-scalemanufacturing enterprises can afford to invest in many robotic systemsand specialize each robotic system to automate a limited set ofproduction tasks, for example, by creating custom mounts for attachingrobotic peripherals to the robotic system, writing custom drivers forthe robotic system to control and interact with active or “smart”robotic peripherals or actuate passive or “dumb” robotic peripherals,and hard coding the robotic system with information about each roboticperipheral, such as its mass, shape, physical extent, attachment site orsites, and the like.

In contrast, small and medium-sized manufacturing enterprises (“SMEs”)typically implement production processes at smaller scales, which limitsSMEs' ability to amortize costs associated with robotic automationthrough production scale. Consequently, SMEs wanting to adopt roboticautomation need to be able to amortize associated costs through otherapproaches, for example, by utilizing robotic systems that can bequickly and efficiently adapted to automate a wide range of productiontasks. A robotic system that offers flexibility in programming, tooling,and user interactions can be adapted to automate different types ofproduction tasks without requiring excessive expenditure of resourcessuch as time, effort, and expertise.

Adaptive robotic retooling apparatus and methods, embodiments of whichare described herein, solve several problems that are typical ofoutfitting a robot in a robotic system with different roboticperipherals (e.g., tools, sensors, end effectors, etc.) to allow therobot to successfully and safely perform actions with the roboticperipherals in the physical world. One, the robotic peripherals must beattached to the robot in a repeatable and rigid manner. This is requiredso that an attached robotic peripheral does not move or come loose whilethe robot performs actions with the attached robotic peripheral. Two,the physical properties of the attached robotic peripheral, such as itsmass, center of mass, moment of inertia, shape, physical extent,interaction or grasping point, must be programmed into the roboticsystem. The size information is required so that interaction point ofthe attached robotic peripheral as well as its shape and extent can befactored into calculations for kinematic movement, collision detection,and other motion calculations. The mass information is used when therobot is equipped with a force sensor and must offset the mass of theattached robotic peripheral, or when the robot is placed into acompliant and gravity-compensated mode for teaching. Three, driverinformation must be retrieved and loaded into the robotic system tocommunicate with and operate the attached robotic peripheral. If therobotic peripheral attached to the robot includes an active peripheral,such as an electrically driven “smart” tool (e.g., a servo), a suitabledriver must be loaded to provide proper power or electrical signals tothe robotic peripheral. In this situation, the driver also communicateswith the robotic peripheral and receives feedback from the roboticperipheral. If the robotic peripheral attached to the robot includes apassive peripheral, such as a pneumatically or hydraulically actuated“dumb” tool, a driver must be loaded that actuates a pneumatic orhydraulic cylinder to cause fluid flow or pressure change to operate therobotic peripheral.

To address the above-described problems, apparatus and methods foradaptive robotic retooling utilize a programmable peripheral adapterthat can attach to the robotic peripheral, store and provide peripheralinformation associated with the robotic peripheral, detachably connectthe robotic peripheral to the robot, and generate connection events thatcause the robotic system to adaptively reconfigure the robot based onthe peripheral information. The programmable peripheral adapter includesan embedded storage unit that stores the peripheral information, such asphysical properties of the robotic peripheral, one or more driverssuitable for operating the robotic peripheral, UI requirements forconfiguring and/or interacting with the robotic peripheral, one or moreimages representative of the robotic peripheral, and the like. Physicalproperties of the robotic peripheral include, for example, a uniqueidentifier, one or more names, one or more models, one or more types, arelative mounting offset, size, mass, a shape, physical extent, typeand/or location of one or more attachment sites, and the like. Theembedded storage unit can also store information associated with theprogrammable peripheral adapter itself, such as physical properties(e.g., a unique identifier, mass, center of mass, thickness, shape,physical extent, type and/or location of one or more attachment points,and the like) of the programmable peripheral adapter, one or more imagesrepresentative of the peripheral adapter, and the like. When theprogrammable peripheral adapter is detachably connects the roboticperipheral to the robot, the programmable peripheral adapter cancommunicate with the robotic system and provide the robotic system withuseful information, which the robotic system uses to reconfigure therobot, update operating characteristics of the robot, and/or communicatewith and operate the robotic peripheral.

FIGS. 1A-C illustrate an embodiment of a robotic retooling apparatus 100that detachably connects a robotic peripheral 80 to a robot 90 in arobotic system and causes the robotic system to adaptively reconfigurerobot 90, consistent with the principles of the present disclosure. Invarious embodiments, an example of which is shown in FIGS. 1A-C, roboticretooling apparatus 100 includes a connector 110 that detachablyconnects a peripheral adapter 120 to a robotic adapter 130. Peripheraladapter 120 has at least two sides, including a flange side and aperipheral side. Robotic adapter 130 also has at least two sides,including a flange side and a robot side. Peripheral adapter 120 canattach to robotic peripheral 80 at the peripheral side of peripheraladapter 120, and robotic adapter 130 can attach to robot 90 at the robotside of robotic adapter 130. If peripheral adapter 120 and roboticadapter 130 are attached to robotic peripheral 80 and robot 90,respectively, then connector 110 can form a detachable connectionbetween robotic peripheral 80 and robot 90. Robotic retooling apparatus100 also includes a docking unit, which is described in greater detailbelow and with respect to FIGS. 4A and 4B, that programs peripheraladapter 120 with information associated with robotic peripheral 80.

Connector 110 detachably connects peripheral adapter 120 to roboticadapter 130, for example, by including a coupling mechanism thatmechanically couples at least one peripheral flange 122 on the flangeside of peripheral adapter 120 with at least one robotic flange 132 onthe flange side of robotic adapter 130. The geometries of connector 110,peripheral flange 122, and robotic flange 132 are shaped such that, whenconnector 110 physically couples (e.g., envelopes, clasps, etc.)peripheral flange 122 and robotic flange 132 together, the couplingmechanism of connector 110 rigidly mates peripheral adapter 120 torobotic adapter 130. For example, the coupling mechanism of connector110 can include a locking mechanism that locks peripheral adapter 120and robotic adapter 130 together to fully constrain peripheral adapter120 and robotic adapter 130 in both position and rotation relative toeach other.

Connector 110 is shown in FIGS. 1A and 1B as a discrete mating collarseparate from peripheral adapter 120 and robotic adapter 130. However,in various embodiments, connector 110 can an integral part of peripheraladapter 120 and/or robotic adapter 130, allowing peripheral adapter 120and robotic adapter 130 to mechanically connect together without adiscrete mating collar. The rotation of peripheral adapter 120 androbotic adapter 130 relative to one another is either constrained byconnector 110 or by one or more alignment features on peripheral adapter120 and robotic adapter 130, such as one or more alignment pins orcomplementarily shaped protrusions.

Peripheral adapter 120 attaches to robotic peripheral 80 at one or moreattachment sites 82 of robotic peripheral 80. Peripheral adapter 120 canbe programmed to store at least one peripheral profile containinginformation associated with robotic peripheral 80, such as a set ofphysical properties of robotic peripheral 80 (e.g., unique identifier,name, model, type, relative mounting offset, size, mass, shape, physicalextent, type and/or location of attachment sites 82, etc.), one or moresuitable drivers that the robotic system can run to operate roboticperipheral 80, UI requirements, one or more images representative ofrobotic peripheral 80, and the like.

Peripheral adapter 120 can also be programmed to store one or moreadapter profiles containing information associated with roboticretooling apparatus 100 or components thereof, such as physicalproperties (e.g., unique identifier, name, mass, thickness, center ofmass, relative mounting offset, shape, physical extent, type and/orlocation of attachment points, and the like) and one or more imagesrepresentative of connector 110, peripheral adapter 120, and/or roboticadapter 130. As described in greater detail infra and with respect toFIGS. 4A and 4B, peripheral adapter 120 includes an embedded datastorage unit and a communication device for storing and communicatinginformation in the peripheral profile of robotic peripheral 80 and/orthe adapter profiles of connector 110, peripheral adapter 120, and/orrobotic adapter 130.

Robotic adapter 130 attaches to robot 90 at a connection site 92 ofrobot 90 and includes a communication device (not shown) thatcommunicatively links with the communication device of peripheraladapter 120 via a physical connection (e.g., connectors, wiredconnections, spring contacts, etc.), a wireless connection (e.g.,Bluetooth, near-field communication (“NFC”), WiFi, RF, optical, etc.),or other means, such as via detectable changes in one or more physicalproperties (e.g., capacitance, resistance, magnetic field, etc.).Robotic retooling apparatus 100 can detect one or more detachableconnections forming between robotic peripheral 80 and robot 90, and inresponse, generate one or more connection events to notify the roboticsystem. With peripheral adapter 120 attached to robotic peripheral 80and robotic adapter 130 attached to robot 90, robotic retoolingapparatus 100 can generate the connection events to notify the roboticsystem of a detachable connection forming between robotic peripheral 80and robot 90.

In various embodiments, robotic retooling apparatus 100 includes aconnection monitor (not shown) that detects a formation of detachableconnections between peripheral adapter 120 and robotic adapter 130,which causes robotic retooling apparatus 100 to respond by generatingone or more connection events and establishing a communication linkbetween peripheral adapter 120 and robotic adapter 130. Roboticretooling apparatus 100 can include the connection monitor as anintegrated part of robotic adapter 130. Robotic retooling apparatus 100can also integrate the connection monitor as a part of connector 110and/or peripheral adapter 120 as well as utilize one or more sensors ofrobotic peripheral 80 or robot 90 as the connection monitor.

The connection monitor can include a mechanical sensor that senses whenperipheral flange 122 and robotic flange 132 are mated and/or whenconnector 110 is installed to mechanically connect peripheral adapter120 to robotic adapter 130. The connection monitor can include a contactsensor that senses a change in capacitance or resistance when peripheraladapter 120 is brought into physical contact with robotic adapter 130.If the communication devices of peripheral adapter 120 and roboticadapter 130 both utilize a wireless communication modality, examples ofwhich includes NFC and Bluetooth, the connection monitor can include aproximity sensor that utilizes either one or both of the communicationdevices to sense when peripheral adapter 120 and robotic adapter 130 arein physical proximity (e.g., within a communication range) of eachother. The connection monitor can include a force sensor that sensesvibration- or acceleration-based force being applied to roboticperipheral 80 and/or robot 90 or a perceived change in mass of robot 90.

When the connection monitor detects a detachable connection formingbetween peripheral adapter 120 and robotic adapter 130, roboticretooling apparatus 100 generates at least one connection event andestablishes a communication link between peripheral adapter 120 androbotic adapter 130. In response to the connection event, the roboticsystem and/or robotic retooling apparatus 100 can alert the user thatthe connection event has taken place via one or more interfacemodalities such as vibration, color, LED display, LED monitor orcellular notification, and the like. Subsequent to establishing thecommunication link, a tool manager (not shown) running on the roboticsystem or robotic retooling apparatus 100 queries peripheral adapter120, which then obtains profile information in a stored peripheralprofile of robotic peripheral 80 and provides the profile information torobot 90 and/or the robotic system. The profile information associatedwith robotic peripheral 80 includes physical properties of roboticperipheral 80, such as the mass, center of mass, moment of inertia,shape, physical extent, interaction or grasping point, or requireddrivers and any other pertinent information that enable robot 90 to userobotic peripheral 80. The tool manager can also query peripheraladapter 120 for profile information in one or more stored adapterprofiles of connector 110, peripheral adapter 120, and/or roboticadapter 130. The profile information associated with components ofrobotic retooling apparatus 100 includes physical properties ofconnector 110, peripheral adapter 120, and/or robotic adapter 130,either individually or in combination when detachably connected. Thetool manager then relays the profile information to robot 90 and/or therobotic system to change system settings, load drivers, actuatemechanical components, etc. If robot 90 is equipped with more than onerobotic adapters, multiple connection events can be interpreted andhandled at once for each robotic peripheral. In this manner, differentrobotic peripherals can be attached to robot 90 simultaneously, and areindividually addressed by the tool manager.

The robotic system can include a peripheral manager (not shown) thatmonitors for connection events, and in response to one or moreconnection events, the peripheral manager communicates with peripheraladapter 120 and/or robotic adapter 130 to obtain relevant profileinformation in the peripheral profile of robotic peripheral 80 and/orthe adapter profiles of the components of robotic retooling apparatus100. Based on the profile information, the robotic system canreconfigure robot 90, load and execute at least one suitable peripheraldriver for communicating with and operating robotic peripheral 80,dynamically generate and adapt UIs for users to interact with roboticperipheral 80 and/or robot 90, and the like. To reconfigure robot 90,robotic system can update at least one robotic profile of robot 90.

In various embodiments, the robotic system stores the robotic profile ofrobot 90 that specifies one or more properties, settings, and/orconfigurations of robot 90 and/or the robotic system. Robotic propertiesof robot 90 include mass-related information, inertia-relatedinformation, dynamics-related information, collision-relatedinformation, control gains-related information, simulation-relatedinformation, logical state-related information, kinematics-relatedinformation, connection site-related information, one or more imagesrepresentative of robot 90, and the like. The robotic system can obtainthe robotic properties associated with robot 90 from the robotic profileof robot 90, utilize the robotic properties to derive the roboticconfiguration of robot 90, and display the robotic configuration ofrobot 90. For example, the robotic system can obtain an imagerepresentative of robot 90 and information related to one or moreconnection sites (e.g., connection site 92) of robot 90, modify theimage to indicate the connection sites' relative locations on robot 90,and display the modified image of robot 90 that visually indicates therelative locations of the connection sites of robot 90.

FIG. 2 illustrates an example process 200 for adaptive retooling ofrobots, consistent with embodiments of the present disclosure. Moreparticularly, robotic retooling apparatus 100 performs process 200 toadaptively retool robots, an example of which includes robot 90 in therobotic system. Process 200 starts at stage 210, during which roboticretooling apparatus 100 identifies robotic peripheral 80 for whichperipheral adapter 120 is designated, programs peripheral adapter 120with at least one peripheral profile of robotic peripheral 80, andattach peripheral adapter 120 to robotic peripheral 80. Peripheraladapter 120 can be designated for robotic peripheral 80 based on userselection and/or properties of peripheral adapter 120, such as size,rigidity, relative mounting offset, type and location of attachmentpoints relative to attachment sites of peripheral adapter 120, and thelike. Robotic retooling apparatus 100 includes a docking unit forprogramming peripheral adapter 120, an example of the docking unitincludes a docking unit 450 shown in FIGS. 4A and 4B and described ingreater detail infra.

At stage 220, robotic retooling apparatus 100 detects a detachableconnection forming between peripheral adapter 120 and robot 90, forexample, via robotic adapter 130 attached to robot 90. Next, at stage230, robotic retooling apparatus 100 generates at least one connectionevent, and then at stage 240, robotic retooling apparatus 100establishes a communication link between robotic adapter 130 and therobotic system, either directly or relayed through robotic adapter 130.

At stage 250, robotic retooling apparatus 100 provides the peripheralprofile of robotic peripheral 80 to the robotic system, which causes therobotic system to adaptively reconfigure robot 90 from an initial statebased on peripheral information in the peripheral profile to a modifiedstate, and thus accounting for robotic peripheral 80. Robotic retoolingapparatus 100 can also provide adapter profiles of peripheral adapter120, robotic adapter 130, and/or connector 110, which the robotic systemto further reconfigure robot 90 based on adapter information in theadapter profiles.

At stage 260, robotic retooling apparatus 100 detects peripheral adapter120 being detached from robot 90, i.e., the detachable connectionbetween peripheral adapter 120 and robot 90 being broken. Finally, atstage 270, robotic retooling apparatus 100 terminates the communicationlink between peripheral adapter 120 and the robotic system.

FIG. 3 illustrates an example process 300 for adaptive retooling ofrobots, consistent with embodiments of the present disclosure. Moreparticularly, the robotic system performs process 300 to adaptivelyretool robots, an example of which includes robot 90 in the roboticsystem. Process 300 starts at stage 310, during which the robotic systemdetects at least one connection event generated by robotic retoolingapparatus 100 and establishes a communication link with peripheraladapter 120. Next, at stage 320, the robotic system queries peripheraladapter 120 for peripheral information stored in the peripheral profileof robotic peripheral 80. The robotic system can also query peripheraladapter 120 for adapter information stored in adapter profiles ofrobotic adapter 130, peripheral adapter 120, and/or connector 110.

Then, at stage 330, the robotic system obtains the peripheralinformation and/or the adapter information, which the robotic systemuses at stage 340 to adaptively reconfigure robot 90 from the initialstate to the modified state, and thus accounting for robotic peripheral80 and/or robotic adapter 130, peripheral adapter 120, and/or connector110. Next, at stage 350, the robotic system obtains a suitableperipheral driver based on the peripheral information, with which therobotic system controls and operates robotic peripheral 90.

At stage 360, the robotic system receives at least one detachment eventindicating that the detachable connection between peripheral adapter 120and robot 90 is broken. Finally, at stage 370, the robotic systemrestores the robotic profile, including operating characteristics andproperties of robot 90, to the initial state, and terminates thecommunication link between peripheral adapter 120 and the roboticsystem.

FIGS. 4A and 4B illustrate an embodiment of a peripheral adapter 420(e.g., peripheral adapter 120 as shown in FIGS. 1A-C) and a docking unit450 of a robotic retooling apparatus (e.g., robotic retooling apparatus100), consistent with the principles of the present disclosure. Invarious embodiments, an example of which is shown in FIGS. 4A and 4B,peripheral adapter 420 has at least two sides, a peripheral flange 422on one side, and one or more peripheral attachment sites 424 on adifferent side, at which peripheral adapter 420 can attach to a roboticperipheral (e.g., robotic peripheral 80) designated for peripheraladapter 420. Peripheral adapter 420 can attach to the robotic peripheralin a manner known to one skilled in the art, such as threaded fasteners,adhesives, welding, friction welding, pins, rivets, etc.

Peripheral adapter 420 includes a communication device 426, which iscommunicatively linked to a data storage unit 428 that is programmableto store a peripheral profile of the robotic peripheral designated forperipheral adapter 420. Communication device 426 matches the modality ofa communication device in a robotic adapter (e.g., robotic adapter 130)and/or a robotic system, and communication device 426 can communicatewith the robotic adapter and/or the robotic system via a physicalconnection (e.g., connectors, wired connections, spring contacts, etc.),a wireless connection (e.g., Bluetooth, NFC, WiFi, RF, optical, etc.),or other means, such as via detectable changes in one or more physicalproperties (e.g., capacitance, resistance, etc.). Data storage unit 428includes a non-volatile, computer-readable storage medium mounted on asubstrate (e.g., a circuit board) or embedded in the structure ofperipheral adapter 420 in a protected fashion.

When peripheral adapter 420 is attached to the robotic peripheral andthe robotic adapter is attached to a robot (e.g., robot 90) in therobotic system, a connector (e.g., connector 110) can detachably connectthe robotic peripheral to the robot. When peripheral adapter 420 isdetachably connected to the robot via the robotic adapter, peripheralflange 422 forms a physical connection to the robot via the connectorand the robotic adapter, and communication device 426 in peripheraladapter 420 forms a communication link with the robotic system via thecommunication device in the robotic adapter or the robotic system.

In various embodiments, when peripheral adapter 420 is docked in dockingunit 450, docking unit 450 programs peripheral adapter 420 with theperipheral profile of the robotic peripheral designated for peripheraladapter 420. Docking unit 450 includes a docking site 452 in whichperipheral adapter 420 can dock, a status indicator 454 that providesstatus information associated with docking unit 450, and a communicationdevice (not shown) that communicatively links with peripheral adapter420. Docking unit 450 also includes a docking application (not shown)running on one or more computer processors in or connected to dockingunit 450 that program peripheral adapter 420 with the peripheralinformation.

When peripheral adapter 420 is docked in docking unit 450, docking site452 securely but detachably hosts peripheral adapter 420. For example,docking site 452 can be shaped to complement and/or accommodate theshape of peripheral flange 422, such that peripheral adapter 420maintains a physical connection to docking unit 450 during docking. Thisconnection need not be as robust as the physical connection formedbetween peripheral adapter 420 and the robotic adapter because duringdocking, peripheral adapter 420 is not subject to the roboticperipheral's operational forces and/or mass. Docking unit 450 includes acommunication device (not shown) that communicates in the same modalityas communication device 426 in peripheral adapter 420. When a user docksperipheral adapter 420 in docking unit 450, for example, by placingperipheral flange 422 in docking site 452, peripheral adapter 420 and/ordocking unit 450 detects peripheral adapter 420 being docked in dockingunit 450 and generates at least one docking event.

In response to the docking event, docking unit 450 establishes acommunication link with communication device 426 in peripheral adapter420 and notifies the user that the communication link has beenestablished via a status indicator 454. For example, status indicator454 can notify the user by displaying one or more colored lights orpatterns, playing one or more musical notes or sound clips, providingone or more vibro-tactile alerts, generating one or more mechanicalmotions, and the like. Subsequent to establishing the communication linkwith peripheral adapter 420, docking unit 450 calls the dockingapplication to query peripheral adapter 420 for the unique identifier ofperipheral adapter 420. If peripheral adapter 420 does not have a uniqueidentifier, for example, because peripheral adapter 420 is a new orblank adapter, then the docking application assigns a unique identifierto peripheral adapter 420. Otherwise, the docking application obtainsthe unique identifier assigned to peripheral adapter 420.

In response to the docking event, docking unit 450 also calls thedocking application to program peripheral adapter 420 with theperipheral profile of the robotic peripheral designated for peripheraladapter 420. Prior to programming peripheral adapter 420, the dockingapplication can provide one or more GUIs for the user to input, modify,and/or confirm the peripheral profile. Alternatively, the dockingapplication can expedite the process of programming peripheral adapter420 by automatically programing peripheral adapter 420 with one or morepre-stored peripheral profiles associated with one or more identicalrobotic peripherals, which would allow the user to efficiently programmultiple peripheral adapters with one or more pre-stored peripheralprofiles. In various embodiments, the docking application canindividually address multiple docking units and use the docking units tosimultaneously program multiple peripheral adapters, i.e., in parallel.

FIG. 5 illustrates an example process for programming peripheraladapters with peripheral profiles of robotic peripherals designated forthe peripheral adapters, consistent with embodiments of the presentdisclosure. Process 500 is performed in docking unit 450. It is desiredthat a robotic peripheral is attached to a robot in a robotic system.The robotic peripheral uses pneumatic pressure to actuate. The usertakes a blank peripheral adapter (i.e., has no information stored inmemory) and places it firmly in docking unit 450. This causes dockingunit 450 to light up blue (visible through status indicator 454) andcauses a tool loader software running on docking unit or an attachedcomputer to initiate. The user uses the tool loader GUI to specifyinformation about the robotic peripheral, such as its mass, inertiatensor, and other physical characteristics, as well as information aboutthe driver needed to run the robotic peripheral (in this case apneumatic system). The user then clicks a button, and this informationis written to the peripheral adapter. This write can be rewritable orpermanent. A security checksum is used to validate the data on theperipheral adapter, and a security key is provided.

The peripheral adapter is now removed from docking unit 450 and affixedto robotic peripheral in some manner. At some later time, the assemblyof the robotic peripheral and the programmed peripheral adapter areplaced against a robotic adapter attached to the robot, and a connectoris used to mate or connect the two together. In response, a connectionevent is inferred and the robotic system obtains peripheral profile datastored on the peripheral adapter, changes the parameters of the robotaccording to the physical parameters and other profile informationassociated with the robotic peripheral, and loads the pneumatic driver.At this time, the user interface on the robot system is changed todenote that the robotic peripheral has been connected, and newinteraction options are available for using or programming actions ofthe robotic peripheral. If the assembly of the robotic peripheral andthe peripheral adapter is removed by removing the connector, anotherrobotic peripheral can be attached and information can be read from itas well. Detaching the robotic peripheral can clear the parameters anddrivers associated with the robotic peripheral.

FIG. 6 illustrates a computer system 600 that is consistent withembodiments of the present disclosure. In general, embodiments ofapparatus and methods for detachably connecting robotic peripherals toadaptively retool robots may be implemented in or performed by variouscomputer systems, such as one or more personal computers, servers,workstations, embedded systems, multifunction devices, or a combinationthereof. Certain embodiments of the systems or modules therein may beembedded as a computer program. The computer program may exist in avariety of forms both active and inactive. For example, the computerprogram can exist as software program(s) comprised of programinstructions in source code, object code, executable code or otherformats; firmware program(s); or hardware description language (“HDL”)files. Any of the above can be embodied on a computer readable medium,which include storage devices and signals, in compressed or uncompressedform. However, for purposes of explanation, system 600 is shown as ageneral purpose computer that is well known to those skilled in the art.Examples of the components and peripherals that may be included insystem 600 will now be described.

As shown, system 600 may include at least one processor 602, a keyboard617, a pointing device 618 (e.g., a mouse, a 3-D pointing device, atouchpad, and the like), a display 616, main memory 610, an input/outputcontroller 615, and a storage device 614. Storage device 614 cancomprise, for example, RAM, ROM, flash memory, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer. A copy of the computer program embodiment ofthe printer driver can be stored on, for example, storage device 614.System 600 may also be provided with additional input/output devices,such as a printer (not shown). The various components of system 600communicate through a system bus 612 or similar architecture. Inaddition, system 600 may include an operating system (“OS”) 620 thatresides in memory 610 during operation. One skilled in the art willrecognize that system 600 may include multiple processors 602. Forexample, system 600 may include multiple copies of the same processor.Alternatively, system 600 may include a heterogeneous mix of varioustypes of processors. For example, system 600 may use one processor as aprimary processor and other processors as co-processors. For anotherexample, system 600 may include one or more multi-core processors andone or more single core processors. Thus, system 600 may include anynumber of execution cores across a set of processors (e.g., processor602). As to keyboard 617, pointing device 618, and display 616, thesecomponents may be implemented using components that are well known tothose skilled in the art. One skilled in the art will also recognizethat other components and peripherals may be included in system 600.

Main memory 610 serves as a primary storage area of system 600 and holdsdata that is actively used by applications, such as the attachmentmanager in the robotic programming platform, running on processor 602.One skilled in the art will recognize that applications are softwareprograms that each contains a set of computer instructions forinstructing system 600 to perform a set of specific tasks duringruntime, and that the term “applications” may be used interchangeablywith application software, application programs, device drivers, and/orprograms in accordance with embodiments of the present teachings. Memory610 may be implemented as a random access memory or other forms ofmemory as described below, which are well known to those skilled in theart.

OS 620 is an integrated collection of routines and instructions that areresponsible for the direct control and management of hardware in system600 and system operations. Additionally, OS 620 provides a foundationupon which to run application software and device drivers. For example,OS 620 may perform services, such as resource allocation, scheduling,input/output control, and memory management. OS 620 may be predominantlysoftware, but may also contain partial or complete hardwareimplementations and firmware. Well known examples of operating systemsthat are consistent with the principles of the present teachings includeROBOT OPERATING SYSTEM, LINUX, UNIX, ORACLE SOLARIS, MICROSOFT WINDOWS,MAC OS, OPEN VMS, and IBM AIX.

The foregoing description is illustrative, and variations inconfiguration and implementation may occur to persons skilled in theart. For instance, the various illustrative logics, logical blocks,modules, and circuits described in connection with the embodimentsdisclosed herein may be implemented or performed with a general purposeprocessor (e.g., processor 602), an application specific integratedcircuit, a field programmable gate array or other programmable logicdevice, discrete gate or transistor logic, discrete hardware components,or any combination thereof designed to perform the functions describedherein. A general-purpose processor may be a microprocessor, but, in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., amicroprocessor, a plurality of microprocessors, or any other suchconfiguration.

In various embodiments, the functions described may be implemented inhardware, software, firmware, or any combination thereof. For a softwareimplementation, the techniques described herein can be implemented withmodules (e.g., procedures, functions, subprograms, programs, routines,subroutines, modules, software packages, classes, and so on) thatperform the functions described herein. A module can be coupled toanother module or a hardware circuit by passing and/or receivinginformation, data, arguments, parameters, or memory contents.Information, arguments, parameters, data, or the like can be passed,forwarded, or transmitted using any suitable means including memorysharing, message passing, token passing, network transmission, and thelike. The software codes can be stored in memory units and executed byprocessors. The memory unit can be implemented within the processor orexternal to the processor, in which case it can be communicativelycoupled to the processor via various means as is known in the art.

If implemented in software, the functions may be stored on ortransmitted over a computer-readable medium as one or more instructionsor code. Computer-readable media includes both tangible, non-transitorycomputer storage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available tangible, non-transitory media thatcan be accessed by a computer. By way of example, and not limitation,such tangible, non-transitory computer-readable media can comprise RAM,ROM, flash memory, EEPROM, CD-ROM or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium that can be used to carry or store desired program code in theform of instructions or data structures and that can be accessed by acomputer. Disk and disc, as used herein, includes CD, laser disc,optical disc, DVD, floppy disk and Blu-ray disc where disks usuallyreproduce data magnetically, while discs reproduce data optically withlasers. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Combinations of the above should also be included within the scope ofcomputer-readable media.

Resources described as singular or integrated can in one embodiment beplural or distributed, and resources described as multiple ordistributed can in embodiments be combined. The scope of the presentteachings is accordingly intended to be limited only by the followingclaims. Although the invention has been described with respect tospecific embodiments, those skilled in the art will recognize thatnumerous modifications are possible. For instance, the proxy servers canhave additional functionalities not mentioned herein. In addition,embodiments of the present disclosure can be realized using anycombination of dedicated components and/or programmable processorsand/or other programmable devices. While the embodiments described abovecan make reference to specific hardware and software components, thoseskilled in the art will appreciate that different combinations ofhardware and/or software components can also be used and that particularoperations described as being implemented in hardware might also beimplemented in software or vice versa.

What is claimed is:
 1. An apparatus for adaptive robotic retooling,comprising: a peripheral adapter including a first side that comprises aperipheral flange, a second side for connecting the peripheral adapterto a robotic peripheral, a peripheral data storage unit for storing aperipheral profile of the robotic peripheral, and a peripheralcommunication device for communicating peripheral information in theperipheral profile, wherein the peripheral data storage unit and theperipheral communication device are communicatively linked; a roboticadapter including a first side that comprises a robotic flange, a secondside for connecting the robotic adapter to a robot, and a roboticcommunication device for providing a communication link with theperipheral communication device; and a connector including a couplingmechanism for mechanically coupling the peripheral flange to the roboticflange, thereby forming a detachable connection between the peripheraladapter and the robotic adapter and causing the robotic adapter toquery, via the communication link, the peripheral adapter for theperipheral information.
 2. The apparatus of claim 1, further comprising:a connection monitor for detecting a formation of the detachableconnection between the peripheral adapter and the robotic adapter andgenerating, in response to detecting the formation of the detachableconnection, a connection event.
 3. The apparatus of claim 2, wherein therobotic adapter includes the connection monitor.
 4. The apparatus ofclaim 2, wherein the connection monitor includes at least one of acontact sensor for detecting the peripheral adapter being in physicalcontact with the robotic adapter, a proximity sensor for detecting theperipheral adapter being within a physical distance of the roboticadapter, or a force sensor for detecting one or more forces beingapplied to the robotic adapter.
 5. The apparatus of claim 2, wherein theperipheral adapter and the robotic adapter establish, in response to theconnection event, the communication link between the roboticcommunication device and the peripheral communication device.
 6. Theapparatus of claim 5, wherein the peripheral data storage unit stores aunique identifier of the peripheral adapter, and wherein the roboticcommunication device of the robotic adapter establishes thecommunication link based on the unique identifier of the peripheraladapter.
 7. The apparatus of claim 2, wherein the robotic adapterprovides, in response to the connection event, the peripheralinformation to a robotic system that includes the robot, and wherein therobotic system modifies one or more robotic properties of the robotbased on the peripheral information.
 8. The apparatus of claim 7,wherein the one or more properties of the robot include at least one ofmass-related information, inertia-related information, dynamics-relatedinformation, collision-related information, control gains-relatedinformation, simulation-related information, logical state-relatedinformation, kinematics-related information, connection site-relatedinformation, or one or more images representative of the robot.
 9. Theapparatus of claim 7, wherein the peripheral profile comprises one ormore properties of the robotic peripheral including at least one ofmass, center of mass, moment of inertia, shape, physical extent, orinteraction point.
 10. The apparatus of claim 7, wherein the peripheralprofile comprises one or more drivers suitable for operating the roboticperipheral.
 11. The apparatus of claim 7, wherein the robotic adapterprovides, in response to the connection event, adapter propertiesassociated with the peripheral adapter to the robotic system, andwherein the robotic system modifies the one or more robotic propertiesof the robot based on the adapter properties, the adapter properties ofthe peripheral adapter including at least one of a mass, center of mass,relative mounting offset, moment of inertia, shape, physical extent, orattachment site to the robotic peripheral.
 12. The apparatus of claim 1,further comprising: a docking unit including a docking monitor fordetecting a formation of a docking connection between the peripheraladapter and a dock communication device for providing a communicationlink with the peripheral communication device of the peripheral adapter,wherein the docking unit obtains a current peripheral profile of therobotic peripheral and causes the peripheral adapter to store thecurrent peripheral profile in the peripheral data storage unit.
 13. Theapparatus of claim 12, wherein the docking unit detects that theperipheral adapter lacks a unique identifier, generates a new uniqueidentifier for the peripheral adapter, and assigns the new uniqueidentifier to the peripheral adapter, thereby causing the peripheraladapter to store the new unique identifier.
 14. The apparatus of claim1, further comprising: a plurality of docking units for docking aplurality of peripheral adapters, obtaining one or more peripheralprofiles of robotic peripherals that are each designated for at leastone of the plurality of peripheral adapters, and simultaneouslyprogramming the plurality of peripheral adapters each with a respectiveone of the one or more peripheral profiles.
 15. The apparatus of claim1, wherein the connector includes a locking mechanism for rigidly matingthe peripheral flange to the robotic flange, thereby causing thedetachable connection to lock the peripheral adapter in position androtation relative to the robotic adapter.
 16. The apparatus of claim 1,wherein the connector is a discrete mating collar separate from theperipheral adapter and the robotic adapter.
 17. The apparatus of claim1, wherein the connector is an integral part of at least one of theperipheral adapter or the robotic adapter.
 18. The apparatus of claim 1,wherein the peripheral communication device and the roboticcommunication device communicate via a communication modality thatincludes at least one of a wired connection, a wireless connection,change in resistance, or change in capacitance.
 19. Acomputer-implemented method for adaptively retooling robots, comprising:detecting a formation of a detachable mechanical connection between aperipheral adapter and a robotic adapter, wherein the peripheral adapteris attached to a robotic peripheral and the robotic adapter is attachedto a robot in a robotic system; establishing, in response to detectingthe formation of the detachable mechanical connection, a communicationlink between the peripheral adapter and the robotic adapter; andproviding, by the peripheral adapter, a peripheral profile of therobotic peripheral to the robotic adapter, wherein the robotic adapterprovides the peripheral profile to the robotic system, thereby causingthe robotic system to obtain a robotic profile of the robot, reconfigurethe robotic profile to provide a reconfigured robotic profile, andoperate the robot based on the reconfigured robotic profile.
 20. Anon-transitory computer-readable storage medium containing instructionswhich, when executed by a processor, perform a method comprising:detecting a formation of a detachable mechanical connection between aperipheral adapter and a robotic adapter, wherein the peripheral adapteris attached to a robotic peripheral and the robotic adapter is attachedto a robot in a robotic system; establishing, in response to detectingthe formation of the detachable mechanical connection, a communicationlink between the peripheral adapter and the robotic adapter; andproviding, by the peripheral adapter, a peripheral profile of therobotic peripheral to the robotic adapter, wherein the robotic adapterprovides the peripheral profile to the robotic system, thereby causingthe robotic system to obtain a robotic profile of the robot, reconfigurethe robotic profile to provide a reconfigured robotic profile, andoperate the robot based on the reconfigured robotic profile.